Skip to content

feat: add steps to rotate creds for ppg integration#7813

Merged
ankur-arch merged 2 commits intomainfrom
DR-8129-rotate-secrets-for-integrations
Apr 21, 2026
Merged

feat: add steps to rotate creds for ppg integration#7813
ankur-arch merged 2 commits intomainfrom
DR-8129-rotate-secrets-for-integrations

Conversation

@ankur-arch
Copy link
Copy Markdown
Contributor

@ankur-arch ankur-arch commented Apr 21, 2026 •
edited by coderabbitai Bot
Loading

Summary by CodeRabbit

  • Documentation
    • Added a new Security section to the Vercel guide covering Prisma integration secret rotation procedures, including step-by-step instructions for configuring delay periods, rotation scope, and redeployment workflows.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 21, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blog Ready Ready Preview, Comment Apr 21, 2026 1:43pm
docs Ready Ready Preview, Comment Apr 21, 2026 1:43pm
eclipse Ready Ready Preview, Comment Apr 21, 2026 1:43pm
site Ready Ready Preview, Comment Apr 21, 2026 1:43pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 21, 2026

🍈 Lychee Link Check Report

10 links: ✅ 5 OK | 🚫 0 errors | 🔀 3 redirects | 👻 2 excluded

✅ All links are working!

Full Statistics Table
Status Count
✅ Successful 5
🔀 Redirected 3
👻 Excluded 2
🚫 Errors 0
⛔ Unsupported 0
⏳ Timeouts 0
❓ Unknown 0

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 21, 2026 •
edited
Loading

Walkthrough

A new Security section was added to the Vercel Postgres guide documentation, containing step-by-step instructions for rotating Prisma integration secrets using the Vercel UI, including configuration, confirmation, and post-rotation verification workflows.

Changes

Cohort / File(s) Summary
Vercel Postgres Guide
apps/docs/content/docs/guides/postgres/vercel.mdx		 Added new Security section with step-by-step instructions for rotating Prisma integration secrets in Vercel UI, including delay period configuration, rotation scope selection, confirmation workflow, redeployment procedures, and connection verification and monitoring guidance.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions 'ppg integration' but the actual changes document rotating credentials for the 'Prisma integration' in Vercel, creating a mismatch between the stated and actual scope. Update the title to accurately reflect the change: 'feat: add steps to rotate credentials for Prisma integration' or similar phrasing that matches the Vercel guide content.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Comment @coderabbitai help to get the list of available commands and usage tips.

coderabbitai[bot]
coderabbitai Bot reviewed Apr 21, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
apps/docs/content/docs/guides/postgres/vercel.mdx (1)

100-113: Add defensive language and a canonical docs link for resilience against UI updates.

While the current Vercel UI labels are accurate—"Installed Products," "Settings," and "Rotate Secrets" are confirmed in the current interface—documentation like this benefits from being resilient to UI evolution. Consider adding a brief note like "labels and navigation may vary slightly depending on your Vercel version" after the introduction, and include a link to the official Vercel secrets rotation documentation as a canonical reference for users to consult if the interface has drifted.

Additionally, frame the April 2026 bulletin as a motivation for the feature rather than the primary context: e.g., "To support incident response and routine credential rotation, Vercel integration partners can rotate secrets via the dashboard. For example, see this incident bulletin." This approach keeps the guide evergreen while still providing helpful context.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@apps/docs/content/docs/guides/postgres/vercel.mdx` around lines 100 - 113,
Update the opening paragraph that starts "In security incidents (like this
Vercel security bulletin…)" to reframe the bulletin as an example rather than
the primary context (e.g., "To support incident response and routine credential
rotation, Vercel integration partners can rotate secrets via the dashboard; for
example, see this Vercel security bulletin…"), add a short defensive note
immediately after that introduction stating "labels and navigation may vary
slightly depending on your Vercel version," and include a canonical reference
link to Vercel’s official secrets rotation docs
(https://vercel.com/docs/integrations/create-integration/secrets-rotation) so
users can consult the authoritative guidance if the UI has changed.
🤖 Prompt for all review comments with AI agents 
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@apps/docs/content/docs/guides/postgres/vercel.mdx`:
- Around line 100-113: Update the opening paragraph that starts "In security
incidents (like this Vercel security bulletin…)" to reframe the bulletin as an
example rather than the primary context (e.g., "To support incident response and
routine credential rotation, Vercel integration partners can rotate secrets via
the dashboard; for example, see this Vercel security bulletin…"), add a short
defensive note immediately after that introduction stating "labels and
navigation may vary slightly depending on your Vercel version," and include a
canonical reference link to Vercel’s official secrets rotation docs
(https://vercel.com/docs/integrations/create-integration/secrets-rotation) so
users can consult the authoritative guidance if the UI has changed.
ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c6281171-f171-46e8-a7d8-481133ec6917

📥 Commits

Reviewing files that changed from the base of the PR and between e45989e and fab5d23.

📒 Files selected for processing (1)
  • apps/docs/content/docs/guides/postgres/vercel.mdx

@argos-ci
Copy link
Copy Markdown

argos-ci Bot commented Apr 21, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ✅ No changes detected - Apr 21, 2026, 1:50 PM

@ankur-arch ankur-arch merged commit 894b7f9 into main Apr 21, 2026
19 checks passed
@ankur-arch ankur-arch deleted the DR-8129-rotate-secrets-for-integrations branch April 21, 2026 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@mhessdev mhessdev mhessdev approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ankur-arch @mhessdev